Good job today, we all had different issues but ended all at the same place. I figured out why we were getting the error in AprilTagDemo.java at the end of the class where is was not finding AprilTagDetectionPipeline. Turns out this class is not within the library but is another demo class same as the AprilTagDemo class we copied . The fix is to also add another file named AprilTagDetectionPipeline.java with the contents of AprilTagDetectionPipeline.java (located at https://github.com/OpenFTC/EOCV-AprilTag-Plugin/blob/master/examples/src/main/java/org/firstinspires/ftc/teamcode/AprilTagDetectionPipeline.java) in the same directory as AprilTagDemo.java . We will do this as the first thing on Monday then start uploading to the robot controller.
Jeff
Good job today, we all had different issues but ended all at the same place. I figured out why we were getting the error in AprilTagDemo.java at the end of the class where is was not finding AprilTagDetectionPipeline. Turns out this class is not within the library but is another demo class same as the AprilTagDemo class we copied . The fix is to also add another file named AprilTagDetectionPipeline.java with the contents of AprilTagDetectionPipeline.java (located at https://github.com/OpenFTC/EOCV-AprilTag-Plugin/blob/master/examples/src/main/java/org/firstinspires/ftc/teamcode/AprilTagDetectionPipeline.java) in the same directory as AprilTagDemo.java . We will do this as the first thing on Monday then start uploading to the robot controller.
For anyone looking for more information on learning how to use Java for coding the FTC robots there is a PDF which shows high level as well as detailed information at https://github.com/alan412/LearnJavaForFTC
Team #22377 The Sigma Corns and Team #19376 Thermal Equilibrium presents CTRL ALT FTC, the most comprehensive Control Theory guide for FIRST Tech Challenge Teams.
I just found a much cleaner way to do global positioning:
newX = x * cos(TWO_PI - IMU_ANGLE) - y * sin(TWO_PI - IMU_ANGLE);
newY = x * sin(TWO_PI - IMU_ANGLE) + y * cos(TWO_PI - IMU_ANGLE);(edited)
@Jeff Could you rename the github repo to something like ftc-code to make things less confusing? Currently it's ftc-2022-23 even though it holds our 2023-24 code.
I added a organization to the ftc22059 account and forked the repo into that organization. You all should have gotten and invite to the organization. When you accept you should be able to push to the repo at https://github.com/FTC22059-members/ftc-2023-24. I created a branch named 2024CenterStage which is the one we will be working on. Zach has tested out the edit ability and it works wo you all should be all set.
I have code that I think will do april tag localization. Should we plan to set up April Tags on Monday to reflect the real game, or should we plan to set up April Tags that are already in the code?(edited)
10:09 AM
If we want to use the Centerstage April Tags, we will need to pull v9.0 of the Teamcode to get them. However, I already have an April Tag setup that is in code.(edited)
I have code that I think will do april tag localization. Should we plan to set up April Tags on Monday to reflect the real game, or should we plan to set up April Tags that are already in the code? (edited)
The Apriltags that are in our codebase is the one for this year. They mentioned that "This year, FIRST Tech Challenge uses a common family called 36h11". We do not know exactly which characters they are using but it we use fromthat family to do localization the code should stay the same with the exception of changing the constants for the tags.
I'm talking about the location of the apriltags. The code in the SDK only detects 36h11 tags.
Alex
If we want to use the Centerstage April Tags, we will need to pull v9.0 of the Teamcode to get them. However, I already have an April Tag setup that is in code. (edited)
The next release for this year (8.3 or 9.0) will not be until after launch so likely not by Monday. I do not think what you have will fundamentally change.
Correct so the code matches the tags they are going to use. As far as the location You have a good range of possible locations in your diagram. Not sure it could possibly be different but your logic likely will work or be very close.
